FAQ and Manuals about cloudn

LBA

This page shows FAQs of LBA.
When you click the question, the answer will be displayed.

How to log “Client IP address” using LBA service

While using LBA service, By default, web servers log golbal IP address, that is LBI’s.

【windows(IIS)】
1. Install “detail log” service additionally (record log is already installed)
2. Customize log fileds with “x-forwarded-for”, whcih is one of the http headers.
3. Restart “detail log”.
4. By default, the messages is logged in [inetpub -> logs -> AdvancedLogs]
*1 : when using apache , same as CentOS
*2 : Value in Timeout for Health Check is set 5 seconds so ClientIP can be logged only every 5 seconds, if you change the value as 1 sec, then it can be logged even within 5 seconds consecutive accesses, however, within 1 sec, there is no way to be logged.

【CentOS(apche)】
1. Edit “LogFormat” directive using “%{X-Forwarded-For}i” in httpd.conf file.

Health check of virtual server under the load balancer fails and OutOfService occurs.

If the health check is not InService, LBA does not functions correctly. In order to make a success of health check and enable LBA, the following conditions are necessary.
1. Layout of index.html
An access to index.html file under Web server is used for health check of virtual server under the load balancer.
Install Web server (such as Apache) and then lay out index.html.

2. Attribute of availability zone (or virtual server’s zone)
LBA has the availability zone as an attribute. If the availability zone is set to jp-e1a, only the instances of jp-e1a are load balanced.
If you want to use jp-e1a and jp-e1b for LBA, you must delete LBA and then create as follows:
 elb-create-lb (LB name) –listener
“lb-port=80,protocol=http,instance-port=80″ –availability-zones “jp-e1a,jp-e1b”

Can I use LBA for streaming?

If you use LBA for streaming in an unchanged condition, the replay may be interrupted.

If you desire the countermeasure against this, submit the tickets and the LBA ID information and request to provide the “LBA streaming countermeasures”.
We change LBA setting so that it is available for streaming.

LBA allocation

If you consider LBA for the FLAT type, the configuration is shown below. When creating a new virtual server, you may need to consider a zone of the said server depending on the situation.

* We don’t provide the function to change the virtual server in Zone A to Zone B after establishment.
You need to change it manually.
* In the LBA configuration where the LBI (LB instance) is across zones, you must use DNS round robin to create a connection configuration.

(LBA configuration where the LBI is not across zones)
               --WEB server 1 (Zone A)
Internet--LBI--│
               --WEB server 2 (Zone A)

(LBA configuration where the LBI is across zones)
                        LBI--WEB server 1 (Zone A)
Internet--DNS round robin--│
                       LBI--WEB server 2 (Zone B)

Linking the LBA service to the DNS service and fees.

We assume that the customer has abc.com actually and LBA setting is finished.

We actually assume four patterns below.
<(1). Use LBA only in the development environment>
<(2). Use abc.com newly in LBA>
<(3). Use only xxx.abc.com in LBA (abc.com is already used separately)>
<(4). Use all of the existing abc.com in the cloud DNS service and use only xxx.abc.com in LBA>

The common procedure is shown below:

===
1. Create the new LBA. At that time, the following line is automatically added.
******-22222222222.lba.jp-e1.cloudn-service.com
2. Place the necessary virtual server under LBA.
===

The procedure differing depending on the condition is shown below:

<(1). Use LBA only in the development environment>
[Procedure]
<(3). Connect with ******-22222222222.lba.jp-e1.cloudn-service.com and confirm on browser. Terminated. <(2). Use abc.com newly in LBA>
[Procedure]
<(3). Purchase a domain (abc.com) from the registrar. 4. According to the DNS manual, create a new zone for abc.com in the cloud DNS service (POST CreateHostedZone). At that time, the following name server is automatically added.
ns-05.dns.jp-e1.cloudn-service.com
ns-06.dns.jp-e1.cloudn-service.com
ns-07.dns.jp-e1.cloudn-service.com

5. Set the information of master name server in whois in the name server obtained in step 4.
6. Associate the FQDN obtained in step 1 when creating LBA, with the zone created in step 4.
===



LBA-Alias-Test


CREATE

abc.com
A

BBB1874A1E3A46
******-22222222222.lba.jp-e1.cloudn-service.com





===
7. Use the browser to connect to abc.com for confirmation.
Terminated.

<(3). Use only xxx.abc.com in LBA (abc.com is already used separately)>
3. Create ******-22222222222.lba.jp-e1.cloudn-service.com as CNAME of xxx in the abc.com zone.
4. Use the browser to connect to xxx.abc.com for confirmation.
Terminated.

<(4). Use all of the existing abc.com in the cloud DNS service and use only xxx.abc.com in LBA>
3. According to the DNS manual, create a new zone for abc.com in the cloud DNS service (POST CreateHostedZone). At that time, the following name server is automatically added.

ns-05.dns.jp-e1.cloudn-service.com
ns-06.dns.jp-e1.cloudn-service.com
ns-07.dns.jp-e1.cloudn-service.com
4. According to the DNS manual, create the existing record (POST
ChangeResourceRecordSets).
5. Change the master name server in the whois database to the name server obtained in step 3.
6. Associate the FQDN obtained in step 1 when creating LBA, with the zone created in step 3,4.
===



LBA-Alias-Test


CREATE

xxx.abc.com
A

BBB1874A1E3A46
******-22222222222.lba.jp-e1.cloudn-service.com





===
7. Use the browser to connect to xxx.abc.com for confirmation.
Terminated.

Lastly for the fees required for four pattern above mentioned, refer to the following site:

http://www.ntt.com/cloudn/data/price.html

1. Fees only for LBA
2. Fees for LBA + DNS
3. Fees only for LBA
4. Fees for LBA + DNS

Can I record the client IP in the Apache logs when using a load balancer?

If you use the Apache setting when using a load balancer, not a client Global IP but a load balancer IP is recorded in those logs.
In order to avoid the above, you can add “%{X-Forwarded-For}i” to LogFormat directive in the Apache configuration file httpd.conf to obtain the client Global IP address.

* However if SSL (443 port) is load-balanced, you cannot record the client IP with the above method.

Can I record the client IP in the nginx logs when using a load balancer?

If you use the nginx setting when using a load balancer, the client Global IP is not recorded in those logs.
In order to avoid the above, you can add two lines below to the nginx configuration file and nginx.conf to show the remote access source IP address in those logs.
set_real_ip_from 10.1.0.1;
real_ip_header X-Forwarded-For;

* However if SSL (443 port) is load-balanced, you cannot record the client IP with the above method.

About security group for LBA.

A Security Group for LBA has following restrictions.
(* A Security Group for RDB is only used for RDB service.)

1. You can’t set not only “CIDR” but also “account” for security group parameter.
(* The status of virtual server under LBA becomes “OutOfService”.)

2. The change of Security Group incomming rule is not refrected once you set a Security Group for LBA.

Does the IP Address associated with LBA DNS name change?

The IP address associated with LBA DNS name may change.

The number of Load Balancer Instance(LBI) increases or decreases depending on the traffic load. When it incerease(scale-out), the number of IP address associated with LBA DNS name also increases. And when scale-in happens, the number of IP address decreases.

Therefore, there is a possibility that IP address associated with LBA DNS name may change because it is not guaranteed that which IP addresses may delete when the scale-in happens. The new IP address may different from initial IP address of LBA DNS name.

Please note above mentioned point that the IP address associated with LBA DNS name is not fixed.

Copyright © Cloudn Information site All Rights Reserved.